Single phase fault isolation and restoration with loop avoidance

ABSTRACT

Techniques for controlling a power distribution network are provided. An electronic processor receives, a fault indication associated with a fault from a first isolation device of a plurality of isolation devices. The processor identifies a first subset of a plurality of phases associated with the fault indication and a second subset of the plurality of phases not associated with the fault indication. The processor identifies a downstream isolation device downstream of the fault. The processor sends send a first open command to the downstream isolation device for each phase in the first subset. The processor sends a close command to a tie-in isolation device for each of the plurality of phases. The processor sends a second open command to the downstream isolation device for each phase in the second subset. Responsive to identifying a potential loop configuration, the processor sends the second open command prior to the close command.

FIELD OF DISCLOSURE

Embodiments described herein relate to electric power distributionnetworks. More particularly, embodiments described herein relate tosystems and methods for providing single phase fault isolation andrestoration with loop avoidance in an electric power distributionnetwork.

SUMMARY

Electric power distribution networks (sometimes referred to as “powerdistribution networks” or “distribution networks”) include faultmonitoring equipment that identifies problems in the system and opensisolation devices to isolate the problems. Example problems with thedistribution system include overcurrent faults, phase-to-phase faults,ground faults, etc. Faults may arise from various causes, for example,equipment failure, weather-related damage to equipment, and others.Switching equipment is provided in the power distribution network toisolate the detected faults. In some instances, a fault may be detectedby an isolation device that is not located closest to the fault. As aresult, power may be interrupted for more customers than necessary.Various isolation devices attempt to reclose to restore power tonon-affected portions of the power distribution network. Powerdistribution networks typically use three-phase transmission lines, andthe isolation devices are controlled to isolate all three-phases inresponse to a detected fault. Even in cases where a particular faultonly involves one or two of the phases, power is interrupted for allcustomers on the affected transmission line.

Embodiments described herein provide, among other things, systems andmethods for providing single phase fault isolation and restoration withloop avoidance in a power distribution network.

One embodiment includes a system for controlling a power distributionnetwork that provides power using a plurality of phases. The systemincludes an electronic processor that is configured to receive a firstfault indication associated with a fault in the power distributionnetwork from a first isolation device of a plurality of isolationdevices. The electronic processor is configured to identify a firstsubset of the plurality of phases associated with the first faultindication and a second subset of the plurality of phases not associatedwith the first fault indication. The first subset and the second subseteach include at least one member. The electronic processor is configuredto identify a downstream isolation device downstream of the fault. Theelectronic processor is configured to send a first open command to thedownstream isolation device for each phase in the first subset, send aclose command to a tie-in isolation device for each of the plurality ofphases, and send a second open command to the downstream isolationdevice for each phase in the second subset. The electronic processor isfurther configured to send the second open command prior to sending theclose command responsive to identifying a potential loop configuration.

Another embodiment includes a method for controlling a powerdistribution network that provides power using a plurality of phases.The method includes receiving, via an electronic processor, a firstfault indication associated with a fault in the power distributionnetwork from a first isolation device of a plurality of isolationdevices. The electronic processor identifies a first subset of theplurality of phases associated with the first fault indication and asecond subset of the plurality of phases not associated with the firstfault indication. The first subset and the second subset each include atleast one member. The electronic processor identifies a downstreamisolation device downstream of the fault. The electronic processor sendsa first open command to the downstream isolation device for each phasein the first subset, sends a close command to a tie-in isolation devicefor each of the plurality of phases, and sends a second open command tothe downstream isolation device for each phase in the second subset. Theelectronic processor sends the second open command prior to sending theclose command responsive to identifying a potential loop configuration.

Other aspects of the disclosure will become apparent by consideration ofthe detailed description and accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a simplified block diagram of a system for controlling singlephase fault isolation in a power distribution network, according to someembodiments.

FIG. 2 is a simplified diagram of a power distribution network,according to some embodiments.

FIG. 3 is a diagram of a switchgear system including an isolationdevice, according to some embodiments.

FIGS. 4A-4F are diagrams illustrating operation of the system of FIG. 1to handle a fault, according to some embodiments.

FIG. 5 is a flowchart of a method for operating the system of FIG. 1 tohandle a fault, according to some embodiments.

FIGS. 6A-6E are diagrams illustrating the operation of the system ofFIG. 1 to handle a loss of voltage fault, according to some embodiments.

FIG. 7 is a flowchart of a method for operating the system of FIG. 1 tohandle a loss of voltage fault, according to some embodiments.

FIGS. 8A-8D are diagrams illustrating the operation of the system ofFIG. 1 to perform a fault restoration operation that avoids loopconfigurations, according to some embodiments.

FIG. 9 is a flowchart of a method for operating the system of FIG. 1 toperform a fault restoration operation that avoids loop configurations,according to some embodiments.

FIGS. 10A-10G are diagrams illustrating the operation of the system ofFIG. 1 to perform a fault restoration operation that avoids loopconfigurations with multiple tie-in isolation devices, according to someembodiments.

FIG. 11 is a flowchart of a method for operating the system of FIG. 1 toperform a fault restoration operation that avoids loop configurationswith multiple tie-in isolation devices, according to some embodiments.

FIGS. 12A-12G are diagrams illustrating the operation of the system ofFIG. 1 to avoid loop configurations, according to some embodiments.

DETAILED DESCRIPTION

One or more embodiments are described and illustrated in the followingdescription and accompanying drawings. These embodiments are not limitedto the specific details provided herein and may be modified in variousways. Furthermore, other embodiments may exist that are not describedherein. Also, the functionality described herein as being performed byone component may be performed by multiple components in a distributedmanner. Likewise, functionality performed by multiple components may beconsolidated and performed by a single component. Similarly, a componentdescribed as performing particular functionality may also performadditional functionality not described herein. For example, a device orstructure that is “configured” in a certain way is configured in atleast that way, but may also be configured in ways that are not listed.Furthermore, some embodiments described herein may include one or moreelectronic processors configured to perform the described functionalityby executing instructions stored in non-transitory, computer-readablemedium. Similarly, embodiments described herein may be implemented asnon-transitory, computer-readable medium storing instructions executableby one or more electronic processors to perform the describedfunctionality. As used herein, “non-transitory computer-readable medium”comprises all computer-readable media but does not consist of atransitory, propagating signal. Accordingly, non-transitorycomputer-readable medium may include, for example, a hard disk, aCD-ROM, an optical storage device, a magnetic storage device, a ROM(Read Only Memory), a RAM (Random Access Memory), register memory, aprocessor cache, or any combination thereof.

Also, the phraseology and terminology used herein is for the purpose ofdescription and should not be regarded as limiting. For example, the useof “including,” “containing,” “comprising,” “having,” and variationsthereof herein is meant to encompass the items listed thereafter andequivalents thereof as well as additional items. The terms “connected”and “coupled” are used broadly and encompass both direct and indirectconnecting and coupling. Further, “connected” and “coupled” are notrestricted to physical or mechanical connections or couplings and caninclude electrical connections or couplings, whether direct or indirect.In addition, electronic communications and notifications may beperformed using wired connections, wireless connections, or acombination thereof and may be transmitted directly or through one ormore intermediary devices over various types of networks, communicationchannels, and connections. Moreover, relational terms such as first andsecond, top and bottom, and the like may be used herein solely todistinguish one entity or action from another entity or action withoutnecessarily requiring or implying any actual such relationship or orderbetween such entities or actions.

FIG. 1 illustrates a system 100 for controlling a power distributionnetwork 105, according to some embodiments. In the example shown, thesystem 100 includes a server 110 communicating with entities in thepower distribution network 105 over one or more communication networks115. In some embodiments, the system 100 includes fewer, additional, ordifferent components than illustrated in FIG. 1. For example, the system100 may include multiple servers 110. The communication network 115employs one or more wired or wireless communication sub-networks orlinks. Portions of the communication network 115 may be implementedusing a wide area network, such as the Internet, a local area network,such as a Bluetooth™ network or Wi-Fi, and combinations or derivativesthereof. In some embodiments, components of the system 100 communicatethrough one or more intermediary devices not illustrated in FIG. 1.

The server 110 is a computing device that may serve as a centralizedresource for controlling entities in the power distribution network 105.As illustrated in FIG. 1, the server 110 includes an electronicprocessor 120, a memory 125, and a communication interface 130. Theelectronic processor 120, the memory 125 and the communication interface130 communicate wirelessly, over one or more communication lines orbuses, or a combination thereof. The server 110 may include additionalcomponents than those illustrated in FIG. 1 in various configurations.The server 110 may also perform additional functionality other than thefunctionality described herein. Also, the functionality described hereinas being performed by the server 110 may be distributed among multipledevices, such as multiple servers included in a cloud serviceenvironment.

The electronic processor 120 includes a microprocessor, anapplication-specific integrated circuit (ASIC), or another suitableelectronic device for processing data. The memory 125 includes anon-transitory computer-readable medium, such as read-only memory (ROM),random access memory (RAM) (for example, dynamic RAM (DRAM), synchronousDRAM (SDRAM), and the like), electrically erasable programmableread-only memory (EEPROM), flash memory, a hard disk, a secure digital(SD) card, another suitable memory device, or a combination thereof. Theelectronic processor 120 is configured to access and executecomputer-readable instructions (“software”) stored in the memory 125.The software may include firmware, one or more applications, programdata, filters, rules, one or more program modules, and other executableinstructions. For example, the software may include instructions andassociated data for performing a set of functions, including the methodsdescribed herein. For example, as illustrated in FIG. 1, the memory 125may store instructions for executing a fault location, isolation, andrestoration (FLISR) unit 135 to control entities in the powerdistribution network 105.

The communication interface 130 allows the server 110 to communicatewith devices external to the server 110. For example, as illustrated inFIG. 1, the server 110 may communicate with entities in the powerdistribution network 105. The communication interface 130 may include aport for receiving a wired connection to an external device (forexample, a universal serial bus (USB) cable and the like), a transceiverfor establishing a wireless connection to an external device (forexample, over one or more communication networks 115, such as theInternet, local area network (LAN), a wide area network (WAN), and thelike), or a combination thereof

FIG. 2 is a simplified diagram of the power distribution network 105,according to some embodiments. In the example shown, the powerdistribution network 105 comprises sources, S1-S3, and isolation devicesR1-R14. The sources S1-S3 and isolation devices R1-R14 are connected bytransmission lines 200. In general, the isolation devices R1-R14 serveto segment the power distribution network 105 so that power is providedvia a single source S1-S3 and to isolate portions of the powerdistribution network 105 in response to identified faults. The isolationdevices R1-R14 may also be referred to as reclosers. Open transmissionlines 200 are illustrated with dashed lines. An open diamond is used inthe figures and placed adjacent an isolation device 305 (as noted, alsoillustrated in some cases as R1-R14) isolating the transmission line 200from a power source. In general, only one source S1-S3 feeds a sectionof the power distribution network 105. Certain isolation devices R1-R14are designated as tie-in isolation devices that allow a different sourceS1-S3 to be tied into a section normally fed by a different sourceS1-S3. For example, the source S2 feeds the transmission lines 200associated with the isolation devices R5, R14, R13, R12. The isolationdevice R12 is in an open state, and is a tie-in isolation device thatmay be closed to provide power from one of the other sources S1, S3.Similarly, isolation devices R7, R9 are tie-in isolation devicesassociated with the source S1. FIG. 2 illustrates the normal operatingconfiguration of the power distribution network 105 with no faults.

FIG. 3 is a diagram of a switchgear system 300 including an isolationdevice 305, according to some embodiments. As noted, the isolationdevice 305 may also be referred to as a recloser. Each of the isolationdevices R1-R14 in FIG. 2 may be configured in a manner that is the sameas or similar to the configuration of the isolation device 305. In theexample provided in FIG. 3, the isolation device 305 receives highvoltage electrical power via a line connection 310 and delivers the highvoltage electrical power via a load connection 315. An interruptingmechanism 320 (for example, a vacuum interrupter) is electricallycoupled between the line connection 310 and the load connection 315 toselectively interrupt current flow therebetween. The switchgear system300 also includes a junction board 325 that is electrically coupled tothe isolation device 305. A controller 330 is electrically coupled tothe junction board 325 via a control cable 335. In FIG. 3, only onephase of the isolation device 305 is illustrated. For ease ofdescription, the other two phases of the three-phase isolation device305 are not shown or described in detail. However, the other two phasesof the three-phase isolation device 305 may include similar componentsas shown in FIG. 3. For example, each of the other two phases mayinclude an interrupting medium, line and load connections, and ajunction board. The controller 330 may be connected to control all thejunction boards 325.

The isolation device 305 automatically tests the electrical line toidentify a fault condition, and automatically opens the line if a faultis detected. In some embodiments, the isolation device 305 opens allthree-phases in response to detecting a fault, for example, anovercurrent fault. The isolation device 305 may operate in a reclosermode or a one-shot mode.

In the recloser mode, the isolation device 305 determines whether thefault condition was only temporary and has resolved and automaticallyresets to close the line and restore electric power. Many troubleconditions on high voltage lines are temporary (for example, lightning,windblown tree branches, windblown transmission lines, animals, etc.),and will, by their nature, remove themselves from the transmission lineif the power is shut off before permanent damage occurs. The isolationdevice 305 senses when trouble occurs and automatically opens to removepower. After a short delay, which may be recognized as or materialize asa lightbulb flicker, for example, the isolation device 305 recloses torestore power. However, if the trouble condition is still present, theisolation device 305 opens again. If the trouble condition persists fora predetermined number of times (for example, three), the isolationdevice 305 locks open and sends a fault notification via the controller330 to a centralized controller, for example the server 110 of FIG. 1executing the FLISR unit 135. Examples of long-lasting or permanentproblem conditions include damaged or down transmission lines, andphysical equipment failure or damage.

In the one-shot mode, the automatic recloser functionality of theisolation device 305 is disabled. If a fault condition is identified,the isolation device 305 locks open and sends a fault indication via thecontroller 330 without attempting to reclose.

Referring to FIGS. 4A-4F and FIG. 5, the operation of the system of FIG.1 is illustrated for a fault. FIGS. 4A-4F are diagrams illustrating theoperation of the system of FIG. 1 for a fault in a portion of the powerdistribution network 105 of FIG. 2, according to some embodiments. FIG.5 is a flowchart of a method 500 for operating of the system of FIG. 1for a fault, according to some embodiments.

In some embodiments, a lockout fault is a fault condition that causesthe isolation device 305 identifying the condition to lock in an openstate. Example lockout fault conditions include voltage faults, phase tophase faults, ground faults, etc. In some embodiments, the isolationdevice 305 signals a fault indication to the FLISR unit 135 of FIG. 1after attempting to reclose a predetermined number of times, asdescribed above.

In some instances, the isolation device 305 that opens or trips is notthe isolation device 305 closest to the fault. For example, thecommunication links between the isolation devices 305 and the FLISR unit135 may have different latencies. For purposes of the following example,assume that a phase to phase fault is present between the R14 isolationdevice 305 and the R13 isolation device 305. FIG. 4A illustrates thepower distribution network 105 prior to any automatic operations, withthe fault illustrated between the R14 and R13 isolation devices 305.

In response to the fault, the R5 isolation device 305 locks open andsends a fault indication (in this example, as indicated by the “!” inthe R5 block). Referring to FIG. 5, a fault indication is received inthe FLISR unit 135 (block 505), for example, from the R5 isolationdevice 305. In some embodiments, the FLISR unit 135 waits for apredetermined time interval (for example, 30 seconds) after receivingthe fault indication before proceeding with restoration operations. Asshown in FIG. 4B, the R5 isolation device 305 is locked open for a firstsubset of the phases that includes the faulted phases, B and C. A secondsubset of the phases includes the non-faulted phase, A.

After receiving fault indication (block 505), the FLISR unit 135attempts to identify the fault location by examining the fault states ofother isolation devices downstream of the fault issuing R5 isolationdevice 305. Isolation devices 305 with asserted faults states areidentified with “!” indicators, and isolation devices 305 with clearfault states are identified with “-” indicators (dashes) in FIG. 4B. Insome embodiments, the isolation devices 305 send fault states atperiodic time intervals, immediately in response to certain events, orin response to a refresh query from the FLISR unit 135.

As shown in block 510, the FLISR unit 135 identifies an upstreamisolation device 305 representing the isolation device 305 immediatelyupstream of the fault, and as shown in block 515, the FLISR unit 135identifies a downstream isolation device 305 representing the isolationdevice 305 immediately downstream of the fault. In the example of FIG.4B, the R14 isolation device 305 is the upstream isolation device 305,and the R13 isolation device 305 is the downstream isolation device 305.In general, the isolation devices 305 downstream of the R5 isolationdevice 305, but positioned before or upstream of the fault, should havethe same fault state as the R5 isolation device 305. The isolationdevice 305 immediately downstream of the fault should have a fault statethat is clear since the fault does not affect the transmission linesassociated with that isolation device 305. In some embodiments, theisolation device 305 that locks out and generates the fault indicationis also the upstream isolation device 305. The FLISR unit 135 identifiesthe isolation device 305 furthest downstream in a string of isolationdevices 305 having a fault state that matches the fault state of thetriggering R5 isolation device 305 as the upstream isolation device (inthis example, the R14 isolation device 305) (block 510). The FLISR unit135 identifies the isolation device 305 downstream of the R14 upstreamisolation device 305 having a fault state that does not register thefault seen by the triggering R5 isolation device as the downstreamisolation device 305 (in this example, the R13 isolation device 305).

As shown in block 520, the FLISR unit 135 identifies a fault mismatch. Afault mismatch is registered in response to an isolation device 305downstream of the triggering R5 isolation device 305 having a faultstate that registers a different fault condition than the fault state ofthe triggering isolation device 305. For example, a mismatch may beidentified in an example where the triggering isolation device 305registers a phase to phase fault affecting phases B and C, and one ofthe downstream isolation devices 305 registers a fault with phase A.Although block 520 is illustrated as being performed after block 515,the mismatch condition is identified concurrently with theidentification of the upstream isolation device 305 (block 510) and theidentification of the downstream isolation device 305 (block 515). Insome embodiments, if a fault mismatch is identified (block 520), theFLISR unit 135 opens all phases of the isolation device 305 prior to thefault mismatch as shown in block 525 and proceeds with three-phaserestoration. If a fault mismatch is not identified (block 520), theFLISR unit 135 proceeds with single phase restoration operations.Alternatively, in some embodiments, the fault state of the triggeringisolation device 305 controls the fault handling, even if one of theisolation devices 305 downstream of the triggering isolation device 305has a fault mismatch.

As shown in block 530, the FLISR unit 135 sends open commands for thefaulted phases in the first subset to the R13 downstream isolationdevice 305, as illustrated in FIG. 4C. In some embodiments, the FLISRunit 135 also sends open commands to the R14 upstream isolation device305 prior to opening the R13 downstream isolation device 305. In aninstance where the isolation device 305 identifying the fault conditionis also the upstream isolation device 305 (in this example, closest tothe fault), the isolation device 305 identifying the fault condition isalready open for the faulted states, and an open command need not besent to the upstream isolation device 305.

As shown in block 535, the FLISR unit 135 sends close commands for thefaulted phases in the first subset to the R5 isolation device 305 thattriggered the fault condition. In an instance where the isolation device305 identifying the fault condition is also the upstream isolationdevice 305 (in this example, closest to the fault), close commands neednot be sent to the upstream isolation device 305. Closing thenon-faulted phases restores power to customers up to the R14 upstreamisolation device 305. In some embodiments, when there are multiplenon-faulted phases, the FLISR unit 135 closes the non-faulted phasesindividually using sequential close commands.

As shown in block 540, the FLISR unit 135 sends close commands for atie-in isolation device 305, as illustrated in FIG. 4E. For example, theR12 isolation device 305 is downstream of the fault and the R13downstream isolation device 305 and can provide power from the sourceS3. In some embodiments, the FLISR unit 135 sends a ganged close commandto the R12 tie-in isolation device 305. In some embodiments, the FLISRunit 135 sends mode messages to the R5, R14, R13, R12, R8, R10, R11isolation devices 305 on the parallel phases to the alternate source S3placing them in one-shot mode prior to sending the close commands. Thus,if one of the isolation devices 305 on the parallel phases trips,automatic reclosing is prevented.

As shown in block 545, the FLISR unit 135 sends open commands to the R13downstream isolation device 305 for the parallel phases (in thisexample, the phases in the second subset), as illustrated in FIG. 4F.For example, the A phase for the R13 isolation device 305 is fed by boththe source S2 and the source S3. Opening the non-faulted phase removesthis parallel source condition. In some embodiments, when there aremultiple non-faulted phases in the second subset, the FLISR unit 135opens the non-faulted phases on the R13 downstream isolation device 305individually using sequential open commands. In some embodiments, aftercompleting the tie-in processing (block 545) without any trips, theFLISR unit 135 sends mode messages to the R15, R14, R13, R12, R8, R10,and R11 isolation devices 305 on the path to both sources S2, S3 placingthem back in reclose mode.

As shown in block 550, the FLISR unit 135 sends fault state resetcommands to the R5 and R14 isolation devices 305 to reset the faultstates and allow fault monitoring to be processed using there-configured the power distribution network 105.

Referring to FIGS. 6A-6E and FIG. 7, the operation of the system of FIG.1 is illustrated for handling a loss of voltage (LOV) fault. FIGS. 6A-6Eare diagrams illustrating the operation of the system of FIG. 1 tohandle an LOV fault in a portion of the power distribution network 105of FIG. 2, according to some embodiments. FIG. 7 is a flowchart of amethod 700 for operating of the system of FIG. 1 for an LOV fault,according to some embodiments.

In some embodiments, an LOV fault is detected by one or more of theisolation devices 305, but does not cause an automatic lockout or tripof the identifying isolation device 305. An LOV fault is defined as anevent where the measured voltage on at least one phase drops below apredefined threshold level. In some embodiments, the predefinedthreshold level (for example, 5-95%) is a user-specified parameter.

Referring to FIG. 7, an LOV fault indication is received as shown inblock 705, for example, from the R2 isolation device 305 (in thisexample, as indicated by the “!” (exclamation mark) in the R2 block). Insome instances, the isolation device 305 that identifies the LOV faultis not the isolation device 305 closest to the fault. For example, thecommunication links between the isolation devices 305 and the FLISR unit135 may have different latencies. For purposes of the following example,assume that the LOV fault is present due to a fault between the R4isolation device 305 and the R6 isolation device 305 on the A phase, andthe R2 isolation device 305 identifies the LOV fault responsive to thevoltage dropping below the predefined threshold. FIG. 6A illustrates thepower distribution network 105 prior to any automatic operations, withthe fault illustrated on the A phase between the R4 and R6 isolationdevices 305. The FLISR unit 135 identifies a first subset of the phasesthat includes the faulted phase, A, and a second subset of the phasesthat includes the non-faulted phases, B and C.

As shown in block 710, the FLISR unit 135 determines if the LOV fault isassociated with an immediate lockout condition. In some embodiments,immediate lockout conditions include the LOV fault occurring at atransformer or at a substation, indicating an equipment failure. If animmediate lockout condition is identified (block 710), the FLISR unit135 initiates a lockout of all phases of the isolation devices 305closest to the LOV fault as shown in block 715.

As shown in block 720, the FLISR unit 135 determines if the LOV fault isassociated with a concurrent underfrequency event. If a concurrentunderfrequency event is identified, the FLISR unit 135 ignores the LOVevent as shown in block 725.

In some embodiments, the FLISR unit 135 waits for a predetermined timeinterval (for example, 30 seconds) after receiving the lockout faultindication before proceeding with restoration operations. As shown inblock 730, the FLISR unit 135 determines if the LOV fault is stillpresent after the predetermined time interval. The FLISR unit 135 mayevaluate the currently reported fault states or send a refresh commandto the isolation devices 305 to evaluate the status of the LOV faultupon expiration of the timer (block 730). If the LOV fault clears (block730), the FLISR unit 135 ignores the LOV fault as shown in block 725. Ifthe LOV fault is still present (block 730), the FLISR unit 135 attemptsto identify the fault location by examining the fault states of otherisolation devices 305 starting from the source S3 and working toward theLOV fault issuing R2 isolation device 305.

As shown in block 740, the FLISR unit 135 identifies a downstreamisolation device 305 representing the isolation device 305 immediatelydownstream of the LOV fault. The FLISR unit 135 starts at the source S3,and evaluates the fault states of the R11, R10, R8, R7, R6, and R4isolation devices 305. Isolation devices 305 with asserted faults statesare identified with “!” indicators, and isolation devices 305 with clearfault states are identified with “-” indicators in FIG. 6B. In theexample of FIG. 6B, the R6 isolation device 305 is the last isolationdevice 305 with a clear fault state, and the R4 isolation device 305 isthe downstream isolation device 305, as it is the first with an assertedLOV fault state. In general, the isolation devices 305 downstream of thefault, for example, the R4, R2, and R3 isolation devices 305, shouldhave the same asserted LOV fault states, and the R6 isolation device 305immediately upstream of the fault should have a LOV fault state that isclear since the fault does not affect the transmission lines associatedwith the R6 isolation device 305. The FLISR unit 135 identifies theisolation device 305 downstream of the R6 isolation device 305 with anasserted LOV fault state as the downstream isolation device 305 (in thisexample, the R4 isolation device 305) (block 740).

As shown in block 745, the FLISR unit 135 identifies a fault mismatch. Afault mismatch is registered in response to the R4 isolation device 305having a fault state that registers a different LOV fault condition thanthe fault state of the R2 triggering isolation device 305. For example,a mismatch may be identified in an example where the R4 isolation device305 registers an LOV affecting phase A, and the R2 triggering isolationdevices 305 registers an LOV fault with a different phase. Althoughblock 745 is illustrated as being performed after block 740, themismatch condition is identified concurrently with the identification ofthe downstream isolation device 305 (block 740). In some embodiments,embodiments, if a fault mismatch is identified (block 745), the FLISRunit 135 opens all phases of the isolation device 305 with the faultmismatch as shown in block 750 and proceeds with three-phaserestoration. If a fault mismatch is not identified (block 745), theFLISR unit 135 proceeds with single phase restoration operations.Alternatively, in some embodiments, the fault state of the triggeringisolation device 305 controls the fault handling, even if one of theisolation devices 305 downstream of the triggering isolation device 305has a fault mismatch.

As shown in block 755, the FLISR unit 135 sends open commands for thephases in the first subset affected by the LOV fault (in this example,the A phase) to the R4 downstream isolation device 305, as illustratedin FIG. 6C. Open transmission lines 200 are illustrated with dashedlines, where an open diamond is adjacent the isolation device 305isolating the transmission line 200 from a power source.

As shown in block 760, the FLISR unit 135 sends close commands for atie-in isolation device 305, as illustrated in FIG. 6D. For example, theR9 isolation device 305 is downstream of the fault and the R4 downstreamisolation device 305 and can provide an alternate path for power fromthe source S3. In some embodiments, the FLISR unit 135 sends a gangedclose command to the R9 tie-in isolation device 305. In someembodiments, the FLISR unit 135 sends mode messages to the R10, R8, R6,R7, R11, R9, R3, R2, and R4 isolation devices 305 on the paralleledphase placing them in one-shot mode prior to sending the close commands.Thus, if one of the isolation devices 305 on the paralleled phasestrips, automatic reclosing is prevented.

As shown in block 765, the FLISR unit 135 sends open commands to the R4downstream isolation device 305 for the non-faulted phases, asillustrated in FIG. 6E. For example, the non-faulted phases in thesecond subset (in this example, the B and C phases) for the R4 isolationdevice 305 are fed by the source S3 from both sides. Opening thenon-faulted phase(s) removes this looped source condition. In someembodiments, when there are multiple non-faulted phases, the FLISR unit135 opens the non-faulted phases on the R4 downstream isolation device305 individually using sequential open commands. In some embodiments,after completing the tie-in processing (block 765) without any trips,the FLISR unit 135 sends mode messages to the R7, R6, R4, R3, R2, R8,R10, and R11 isolation devices 305 placing them back in reclose mode.

Referring to FIGS. 8A-8D and FIG. 9, the operation of the system of FIG.1 to perform a fault restoration operation that avoids loopconfigurations is illustrated. FIGS. 8A-8D are diagrams illustrating theoperation of the system of FIG. 1 to avoid loop configurations duringfault restoration in a portion of the power distribution network 105 ofFIG. 2, according to some embodiments. FIG. 9 is a flowchart of a method900 for operating of the system of FIG. 1 to avoid loop configurationsduring fault restoration, according to some embodiments. For purposes ofthis illustration, a loop configuration is defined as a configurationwhere the same source feeds both the faulted line section and the tie-inisolation device 305. The processing of FIGS. 8A-8D and FIG. 9 may becombined with the methods described above in FIGS. 5 and 7.

As shown in block 905, a fault indication is received. In someembodiments, the fault indication is a lockout fault (for example,current fault, phase to phase fault, ground fault, etc.) In someembodiments, the fault indication is an LOV fault. For purposes ofdiscussion, the fault received in block 905 is an LOV fault presentbetween the R6 and R4 isolation devices 305, as shown in FIG. 8A. Asdescribed above, any of the isolation devices 305 downstream of thefault may register the LOV event, such as the R4, R2, or R3 isolationdevices. In this example, the R6 isolation device 305 registers thefault, as indicated by the “!” in the R6 block. If one of the otherisolation devices 305 registered the fault, the FLISR unit 135 evaluatesthe fault states to identify the isolation device 305 closest to thefault, as described above in reference to FIG. 7.

As shown in block 910 and FIG. 8B, the FLISR unit 135 isolates thefault. In some embodiments, the FLISR unit 135 isolates the fault byopening the subset of the phases associated with the fault on thedownstream isolation device, which in the example of FIGS. 8A-8D, is the“A” phase of the R4 isolation device 305. In some embodiments, where thefault is a lockout fault, the isolation device 305 that initiates thefault detection and initially opens is not the isolation device 305closest to the fault. In such a scenario, the FLISR unit 135 alsoidentifies and opens subset of the phases associated with the fault forthe upstream isolation device as described above in reference to FIG. 5.

As shown in block 915, the FLISR unit 135 identifies one or more tie-inisolation devices 305 that should be closed to restore power to linesdownstream of the fault. In the example of FIGS. 8A-8D, the tie-inisolation device 305 is the R9 isolation device 305.

In block 920, the FLISR unit 135 determines if a potential loopconfiguration is associated with the closing of the tie-in isolationdevice 305. In some embodiments, the FLISR unit 135 identifies apotential loop configuration responsive to the tie-in isolation device305 being supplied by the same source as the faulted isolation device305. In this example, the R4 isolation device 305 associated with thefaulted phase is supplied by the source S3, and the alternate source forthe R9 tie-in isolation device 305 is also supplied by the source S3, sothe potential loop configuration is present in block 920.

Responsive to a potential loop configuration not being present in block920, the FLISR unit 135 follows the process described above in referenceto FIGS. 5 and 7 by sending a close command to the tie-in isolationdevice 305 as shown in block 925 and sending an open command to thedownstream isolation device 305 for the non-faulted phases in block 930.

In this example, a potential loop configuration is associated with theclosing of the R9 tie-in isolation device 305. Responsive to a potentialloop configuration being present in block 920, the FLISR unit 135 sendsan open command to the R4 downstream isolation device 305 for thenon-affected phases (in this example, the phases in the second subset)in block 935, as illustrated in FIG. 8C.

As shown in block 940, the FLISR unit 135 sends a close command to theR9 tie-in isolation device 305, as illustrated in FIG. 8D. In someembodiments, the FLISR unit 135 sends a ganged close command to the R9tie-in isolation device 305. Opening the non-affected phases of the R4isolation device 305 in block 935 prior to closing the R9 tie-inisolation device 305 avoids the loop configuration.

Referring to FIGS. 10A-10G and FIG. 11, the operation of the system ofFIG. 1 to perform a fault restoration operation that avoids loopconfigurations associated with multiple tie-in isolation devices 3051 isillustrated. FIGS. 10A-10G are diagrams illustrating the operation ofthe system of FIG. 1 to avoid loop configurations with multiple tie-inisolation devices 305 during fault restoration in a portion of the powerdistribution network 105 of FIG. 2, according to some embodiments. FIG.11 is a flowchart of a method 1100 for operating of the system of FIG. 1to avoid loop configurations during fault restoration with multipletie-in isolation devices 305, according to some embodiments. Forpurposes of this illustration, a loop configuration is defined as aconfiguration where the multiple tie-in isolation devices 305 are fed bythe same source. The processing of FIGS. 10A-10G and FIG. 11 may becombined with the methods described above in FIGS. 5 and 7.

As shown in block 1105, a fault indication is received. In someembodiments, the fault indication is a lockout fault (for example,current fault, phase to phase fault, ground fault, etc.) In someembodiments, the fault indication is an LOV fault. For purposes ofdiscussion, the fault received in block 1105 is a lockout fault on the“A” phase present between the R1, R4, and R2 isolation devices 305, asshown in FIG. 10A. The lockout fault is identified by the R1 isolationdevice 305 (in this example, as indicated by the “!” in the R1 block).In the example of FIG. 10A, the R1 isolation device 305 is both theisolation device that identifies and locks out the fault condition andthe isolation device 305 closest to the fault (in this example, theupstream isolation device 305 in the context of FIG. 5). If a differentisolation device 305 upstream of the R1 isolation device registers thefault, the FLISR unit 135 evaluates the fault states to identify theupstream isolation device 305 closest to the fault, as described abovein reference to FIG. 5.

As shown in block 1110 and FIG. 10B, the FLISR unit 135 isolates thefault. In some embodiments, the FLISR unit 135 isolates the fault byopening the subset of the phases associated with the fault on thedownstream isolation device, which in the example of FIGS. 10A-10G, isthe “A” phase of the R4 and R2 isolation devices 305.

As shown in block 1115, the FLISR unit 135 identifies one or more tie-inisolation devices 305 that should be closed to restore power to linesdownstream of the fault. In the example of FIGS. 10A-10G, the tie-inisolation devices 305 include the R7 and R9 isolation devices 305. TheR7 tie-in isolation device 305 is associated with the R4 downstreamisolation device 305, and the R9 tie-in isolation device 305 isassociated with the R2 downstream isolation device 305.

In block 1120, the FLISR unit 135 determines if a potential loopconfiguration is associated with the closing of multiple tie-inisolation devices 305. In some embodiments, the FLISR unit 135identifies a potential loop configuration responsive to multiple tie-inisolation devices 305 being supplied by the same source. In thisexample, the R7 and R9 tie-in isolation devices 305 are supplied by thesource S3, so the loop configuration is present in block 1120.

If a potential loop configuration is not present in block 1120 (forexample, multiple tie-in isolation devices 305 supplied by differentsources), the FLISR unit 135 follows the process described above inreference to FIGS. 5 and 7 by closing the multiple tie-in isolationdevices 305 as shown in block 1125 and sending an open command to thedownstream isolation device 305 for the non-faulted phases in block1130.

In this example, a potential loop configuration is associated with theR7 and R9 tie-in isolation devices 305. Closing the R7 and R9 tie-inisolation devices 305 would create a loop because the source S3 iscommon to both the R7 and R9 tie-in isolation devices 305. Responsive toa multiple tie-in potential loop configuration being present in block1120, the FLISR unit 135 processes the tie-in isolation devices 305individually, as shown in block 1135.

As shown in block 1140, the FLISR unit 135 sends a close command to thetie-in isolation device 305 and send an open command to the downstreamisolation device 305 associated with the tie-in isolation device 305 forthe non-faulted phases. When processing each tie-in isolation device305, the FLISR unit 135 also evaluates the loop configuration asdescribed in the method 900 of FIG. 9 for a single tie-in isolationdevice 305. Hence, the order of the close command and the open commandmay vary, as shown in FIG. 9.

Since the R7 tie-in isolation device 305 does not have the same source(for example, source S3) that was feeding the faulted line section (forexample, source S1), the FLISR unit 135 sends a close command to the R7tie-in isolation device 305 (block 925 of FIG. 9), as illustrated inFIG. 10D followed by an open command to the R4 downstream isolationdevice 305 associated with the R7 tie-in isolation device for thenon-faulted phases (block 930 of FIG. 9), as illustrated in FIG. 10E. Insome embodiments, the FLISR unit 135 sends a ganged close command to theR7 tie-in isolation device 305.

As shown in block 1145, the FLISR unit 135 determines if another tie-inisolation device 305 remains to be processed. In this example, the R9isolation device 305 is still pending. Responsive to an unprocessedtie-in isolation device 305 remaining in block 1145, the FLISR unit 135returns to block 1140.

Since the R9 tie-in isolation device 305 does not have the same source(for example, source S3) that was feeding the faulted line section (forexample, source S1), the FLISR unit 135 sends a close command to the R9tie-in isolation device 305 (block 925 of FIG. 9), as illustrated inFIG. 10F followed by an open command to the R2 downstream isolationdevice 305 associated with the R9 tie-in isolation device 305 for thenon-faulted phases (block 930 of FIG. 9), as illustrated in FIG. 10G. Insome embodiments, the FLISR unit 135 sends a ganged close command to theR9 tie-in isolation device 305.

If no unprocessed tie-in isolation devices 305 are present in block1145, the method 1100 terminates at clock 1150. Processing the multipletie-in isolation devices 305 with a common source individually avoidsloop configurations.

FIGS. 12A-12G are diagrams illustrating the operation of the system ofFIG. 1 to avoid loop configurations according to the method 1100 of FIG.11, according to some embodiments. The fault condition is similar tothat illustrated in FIG. 10A. At the point illustrated in FIG. 12A, theFLISR unit 135 has isolated the fault by opening the subset of thephases associated with the fault on the downstream isolation devices,which in the example of FIGS. 12A-12G, is the “A” phase of the R15, R4,and R2 isolation devices 305. The R7 tie-in isolation device 305 isassociated with the R4 downstream isolation device 305, the R9 tie-inisolation device 305 is associated with the R2 downstream isolationdevice 305, and the R16 tie-in isolation device 305 is associated withthe R15 downstream isolation device 305.

In the example illustrated in FIG. 12A, three tie-in isolation devices305 are present, the R16, R7, and R9 tie-in isolation devices 305. Sincethe R7 and R9 tie-in isolation devices 305 share a common source S3, thetie-in isolation devices 305 are processed individually according to themultiple tie-in loop configuration identified in block 1120 of FIG. 11.

In the illustrated example, the FLISR unit 135 starts with the R9isolation device 305 at block 1140. Since the R9 tie-in isolation device305 does not have the same source (for example, source S3) that wasfeeding the faulted line section (for example, source S1), the FLISRunit 135 sends a close command to the R9 tie-in isolation device 305(block 925 of FIG. 9), as illustrated in FIG. 12B followed by an opencommand to the R2 downstream isolation device 305 for the non-faultedphases (block 930 of FIG. 9), as illustrated in FIG. 12C. In someembodiments, the FLISR unit 135 sends a ganged close command to the R9tie-in isolation device 305.

As shown in block 1145, the FLISR unit 135 determines if another tie-inisolation device 305 to be processed. In this example, the R16 and R7isolation devices 305 are still pending. Responsive to an unprocessedtie-in isolation device 305 remaining in block 1145, the FLISR unit 135returns to block 1140 to process the R16 tie-in isolation device 305.

In this example, the R16 tie-in isolation device 305 does have the samealternate source (for example, source S1) that was feeding the faultedline section (for example, source S1), so a loop configuration ispresent in block 920 of FIG. 9. The FLISR unit 135 sends an open commandto the R15 downstream isolation device 305 for the non-faulted phases(block 935 of FIG. 9), as illustrated in FIG. 12D followed by a closecommand to the R16 tie-in isolation device 305 (block 940 of FIG. 9), asillustrated in FIG. 12E. In some embodiments, the FLISR unit 135 sends aganged close command to the R16 tie-in isolation device 305.

As shown in block 1145, the FLISR unit 135 determines if another tie-inisolation device 305 remains to be processed. In this example, the R7isolation device 305 is still pending. Responsive to an unprocessedtie-in isolation device 305 remaining in block 1145, the FLISR unit 135returns to block 1140 to process the R7 tie-in isolation device 305.

Since the R7 tie-in isolation device 305 does not have the same source(for example, source S3) that was feeding the faulted line section (forexample, source S1), the FLISR unit 135 sends a close command to the R7tie-in isolation device 305 (block 925 of FIG. 9), as illustrated inFIG. 12F followed by an open command to the R15 downstream isolationdevice 305 for the non-faulted phases (block 930 of FIG. 9), asillustrated in FIG. 12G. In some embodiments, the FLISR unit 135 sends aganged close command to the R7 tie-in isolation device 305.

Among other things, the techniques described herein isolate faults andrestore power using an individual phase approach. This approachincreases system utilization by reducing the number of customersexperiencing power outages as a result from a fault condition, therebyincreasing customer satisfaction and preserving revenue generated by thenon-affected phases.

In some embodiments, the FLISR unit implements fault processing whileperforming the method 900 of FIG. 9 or the method 1100 of FIG. 11.Consider the example illustrated in 12B where the FLISR unit sent aclose command to the R9 tie-in isolation device 305 (block 925 of FIG.9) followed by an open command to the R2 downstream isolation device 305for the non-faulted phases (block 930 of FIG. 9). In this example, theR2 isolation device 305 fails to respond to the open command. Thisfailure to respond may be the result of a communication error orequipment failure. The FLISR unit 135 identifies a FLISR processingexception when it fails to receive a confirmation that the R2 isolationdevice 305 implemented the open command within a predetermined timeperiod. As seen in FIG. 12B, a parallel source condition exists wherethe source S1 and the source S3 are both supplying the non-faultedphases associated with the R2 downstream isolation device 305. Inresponse to the FLISR unit 135 identifying the FLISR processingexception and determining that at the faulted step, a parallel sourcecondition exists, the FLISR unit 135 opens the R9 tie-in isolationdevice to remove the parallel source condition. The FLISR unit 135generates a failure report including a FLISR processing exceptionindicator, the action taken, and the steps remining after the FLISRfault that were not completed. In this example, the remaining stepsinclude the commands to process the R16 and R7 tie-in isolation devices305.

Consider another example illustrated in 12D where the FLISR unit sent anopen command to the R15 downstream isolation device 305 for thenon-faulted phases (block 935 of FIG. 9), followed by a close command tothe R16 tie-in isolation device 305 (block 940 of FIG. 9). In thisexample, the R16 tie-in isolation device 305 fails to respond to theclose command. This failure to respond may be the result of acommunication error or equipment failure. The FLISR unit 135 identifiesa FLISR processing exception when it fails to receive a confirmationthat the R16 tie-in isolation device 305 implemented the close commandwithin a predetermined time period. As seen in FIG. 12D, because theorder of the close command to the R16 tie-in isolation device 305 andthe open command to the R15 downstream isolation device 305 was reversedto avoid a loop configuration, a parallel source condition does notexist. The source S1 does not supply the non-faulted phases associatedwith the R15 downstream isolation device 305.

In response to the FLISR unit 135 identifying the FLISR processingexception and determining that at the faulted step, a parallel sourcecondition does not exist, the FLISR unit 135 need not take anyadditional action. The FLISR unit 135 generates a failure reportincluding a FLISR processing exception indicator and the steps reminingafter the FLISR fault that were not completed. In this example, theremaining steps include the commands to process the R7 tie-in isolationdevice 305.

The following examples illustrate example systems and methods describedherein.

Example 1: a system for controlling a power distribution networkproviding power using a plurality of phases, the system comprising: anelectronic processor configured to: receive a first fault indicationassociated with a fault in the power distribution network from a firstisolation device of a plurality of isolation devices; identify a firstsubset of the plurality of phases associated with the first faultindication and a second subset of the plurality of phases not associatedwith the first fault indication, wherein the first subset and the secondsubset each include at least one member; identify a downstream isolationdevice downstream of the fault; send a first open command to thedownstream isolation device for each phase in the first subset; send aclose command to a tie-in isolation device for each of the plurality ofphases; and send a second open command to the downstream isolationdevice for each phase in the second subset, wherein the electronicprocessor is further configured to send the second open command prior tosending the close command responsive to identifying a potential loopconfiguration.

Example 2: the system of example 1, wherein the electronic processor isconfigured to: identify the potential loop configuration responsive to afirst source supplying the downstream isolation device and the tie-inisolation device.

Example 3: the system of examples 1-2, wherein the electronic processoris configured to: identify a processing exception associated with thesending of the first open command, the close command, or the second opencommand; and generate an exception report indicating the processingexception and uncompleted steps associated with the processing of thefirst fault indication.

Example 4: the system of examples 1-3, wherein the electronic processoris configured to: identify a processing exception responsive to thedownstream isolation device failing to execute the second open command;and send a third open command to the tie-in isolation device for each ofthe plurality of phases responsive to identifying the processingexception.

Example 5: the system of examples 1-4, wherein the electronic processoris configured to: identify an upstream isolation device upstream of thefault; and responsive to the first isolation device not being theupstream isolation device, send a close command to the first isolationdevice for each phase in the first subset.

Example 6: the system of examples 1-5, wherein the electronic processoris configured to identify the upstream isolation device by: receivingfault states of the plurality of isolation devices; and designating afirst selected isolation device positioned furthest downstream of afirst source in the power distribution network having a fault stateconsistent with the first fault indication as the upstream isolationdevice.

Example 7: the system of examples 1-6, wherein the electronic processoris configured to: identify the downstream isolation device bydesignating a second selected isolation device positioned downstream ofthe upstream isolation device having a fault state that does notindicate the first fault indication as the downstream isolation device,

Example 8: the system of examples 1-7, wherein the electronic processoris configured to: send the close command to the tie-in isolation deviceby sending a ganged close command to concurrently close all of thephases of the tie-in isolation device.

Example 9: the system of examples 1-8, wherein the fault comprises alockout fault that results in the first isolation device opening thefirst subset of the plurality of phases.

Example 10: the system of examples 1-9, wherein the fault comprises aloss of voltage fault.

Example 11: a method for controlling a power distribution networkproviding power using a plurality of phases, the method comprising:receiving, via an electronic processor, a first fault indicationassociated with a fault in the power distribution network from a firstisolation device of a plurality of isolation devices; identifying, viathe electronic processor, a first subset of the plurality of phasesassociated with the first fault indication and a second subset of theplurality of phases not associated with the first fault indication,wherein the first subset and the second subset each include at least onemember; identifying, via the electronic processor, a downstreamisolation device downstream of the fault; sending, via the electronicprocessor, a first open command to the downstream isolation device foreach phase in the first subset; sending, via the electronic processor, aclose command to a tie-in isolation device for each of the plurality ofphases; and sending, via the electronic processor, a second open commandto the downstream isolation device for each phase in the second subset,wherein the electronic processor is further configured to send thesecond open command prior to sending the close command responsive toidentifying a potential loop configuration.

Example 12: the method of example 11, comprising: identifying, via theelectronic processor, the potential loop configuration responsive to afirst source supplying the downstream isolation device and the tie-inisolation device.

Example 13: the method of examples 10-12, comprising: identifying, viathe electronic processor, a processing exception associated with thesending of the first open command, the close command, or the second opencommand; and generating, via the electronic processor, an exceptionreport indicating the processing exception and uncompleted stepsassociated with the processing of the first fault indication.

Example 14: the method of examples 10-13, comprising: identifying, viathe electronic processor, a processing exception responsive to thedownstream isolation device failing to execute the second open command;and sending, via the electronic processor, a third open command to thetie-in isolation device for each of the plurality of phases responsiveto identifying the processing exception.

Example 15: the method of examples 10-14, comprising: identifying, viathe electronic processor, an upstream isolation device upstream of thefault; and responsive to the first isolation device not being theupstream isolation device, sending, via the electronic processor, aclose command to the first isolation device for each phase in the firstsubset.

Example 16: the method of examples 10-15, comprising: identifying theupstream isolation device by receiving, via the electronic processor,fault states of the plurality of isolation devices; and designating, viathe electronic processor, a first selected isolation device positionedfurthest downstream of a first source in the power distribution networkhaving a fault state consistent with the first fault indication as theupstream isolation device.

Example 17: the method of examples 10-16, comprising: identifying, viathe electronic processor, the downstream isolation device by designatinga second selected isolation device positioned downstream of the upstreamisolation device having a fault state that does not indicate the firstfault indication as the downstream isolation device.

Example 18: the method of examples 10-17, comprising: sending, via theelectronic processor, the close command to the tie-in isolation deviceby sending a ganged close command to concurrently close all of thephases of the tie-in isolation device.

Example 19: the method of examples 10-18, wherein the fault comprises alockout fault that results in the first isolation device opening thefirst subset of the plurality of phases.

Example 20: the method of examples 10-19, wherein the fault comprises aloss of voltage fault.

Various features and advantages of the embodiments described herein areset forth in the following claims.

What is claimed is:
 1. A system for controlling a power distributionnetwork providing power using a plurality of phases, the systemcomprising: an electronic processor configured to: receive a first faultindication associated with a fault in the power distribution networkfrom a first isolation device of a plurality of isolation devices;identify a first subset of the plurality of phases associated with thefirst fault indication and a second subset of the plurality of phasesnot associated with the first fault indication, wherein the first subsetand the second subset each include at least one member; identify adownstream isolation device downstream of the fault; send a first opencommand to the downstream isolation device for each phase in the firstsubset; send a close command to a tie-in isolation device for each ofthe plurality of phases; and send a second open command to thedownstream isolation device for each phase in the second subset, whereinthe electronic processor is further configured to send the second opencommand prior to sending the close command responsive to identifying apotential loop configuration.
 2. The system of claim 1, wherein theelectronic processor is configured to: identify the potential loopconfiguration responsive to a first source supplying the downstreamisolation device and the tie-in isolation device.
 3. The system of claim1, wherein the electronic processor is configured to: identify aprocessing exception associated with the sending of the first opencommand, the close command, or the second open command; and generate anexception report indicating the processing exception and uncompletedsteps associated with the processing of the first fault indication. 4.The system of claim 1, wherein the electronic processor is configuredto: identify a processing exception responsive to the downstreamisolation device failing to execute the second open command; and send athird open command to the tie-in isolation device for each of theplurality of phases responsive to identifying the processing exception.5. The system of claim 1, wherein the electronic processor is configuredto: identify an upstream isolation device upstream of the fault; andresponsive to the first isolation device not being the upstreamisolation device, send a close command to the first isolation device foreach phase in the first subset.
 6. The system of claim 5, wherein theelectronic processor is configured to identify the upstream isolationdevice by: receiving fault states of the plurality of isolation devices;and designating a first selected isolation device positioned furthestdownstream of a first source in the power distribution network having afault state consistent with the first fault indication as the upstreamisolation device.
 7. The system of claim 6, wherein the electronicprocessor is configured to: identify the downstream isolation device bydesignating a second selected isolation device positioned downstream ofthe upstream isolation device having a fault state that does notindicate the first fault indication as the downstream isolation device.8. The system of claim 7, wherein the electronic processor is configuredto: send the close command to the tie-in isolation device by sending aganged close command to concurrently close all of the phases of thetie-in isolation device.
 9. The system of claim 1, wherein the faultcomprises a lockout fault that results in the first isolation deviceopening the first subset of the plurality of phases.
 10. The system ofclaim 1, wherein the fault comprises a loss of voltage fault.
 11. Amethod for controlling a power distribution network providing powerusing a plurality of phases, the method comprising: receiving, via theelectronic processor, a first fault indication associated with a faultin the power distribution network from a first isolation device of aplurality of isolation devices; identifying, via the electronicprocessor, a first subset of the plurality of phases associated with thefirst fault indication and a second subset of the plurality of phasesnot associated with the first fault indication, wherein the first subsetand the second subset each include at least one member; identifying, viathe electronic processor, a downstream isolation device downstream ofthe fault; sending, via the electronic processor, a first open commandto the downstream isolation device for each phase in the first subset;sending, via the electronic processor, a close command to a tie-inisolation device for each of the plurality of phases; and sending, viathe electronic processor, a second open command to the downstreamisolation device for each phase in the second subset, wherein theelectronic processor is further configured to send the second opencommand prior to sending the close command responsive to identifying apotential loop configuration.
 12. The method of claim 11, comprising:identifying, via the electronic processor, the potential loopconfiguration responsive to a first source supplying the downstreamisolation device and the tie-in isolation device.
 13. The method ofclaim 11, comprising: identifying, via the electronic processor, aprocessing exception associated with the sending of the first opencommand, the close command, or the second open command; and generating,via the electronic processor, an exception report indicating theprocessing exception and uncompleted steps associated with theprocessing of the first fault indication.
 14. The method of claim 11,comprising: identifying, via the electronic processor, a processingexception responsive to the downstream isolation device failing toexecute the second open command; and sending, via the electronicprocessor, a third open command to the tie-in isolation device for eachof the plurality of phases responsive to identifying the processingexception.
 15. The method of claim 11, comprising: identifying, via theelectronic processor, an upstream isolation device upstream of thefault; and responsive to the first isolation device not being theupstream isolation device, sending, via the electronic processor, aclose command to the first isolation device for each phase in the firstsubset.
 16. The method of claim 15, comprising: identifying the upstreamisolation device by receiving, via the electronic processor, faultstates of the plurality of isolation devices; and designating, via theelectronic processor, a first selected isolation device positionedfurthest downstream of a first source in the power distribution networkhaving a fault state consistent with the first fault indication as theupstream isolation device.
 17. The method of claim 16, comprising:identifying, via the electronic processor, the downstream isolationdevice by designating a second selected isolation device positioneddownstream of the upstream isolation device having a fault state thatdoes not indicate the first fault indication as the downstream isolationdevice.
 18. The method of claim 17, comprising: sending, via theelectronic processor, the close command to the tie-in isolation deviceby sending a ganged close command to concurrently close all of thephases of the tie-in isolation device.
 19. The method of claim 11,wherein the fault comprises a lockout fault that results in the firstisolation device opening the first subset of the plurality of phases.20. The method of claim 11, wherein the fault comprises a loss ofvoltage fault.